home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
rmail181.zip
/
EXAMPLE.CFG
< prev
next >
Wrap
Text File
|
1992-02-21
|
8KB
|
194 lines
; CONFIG file for RBBSMAIL v18.0beta9
; All lines with a ';' in colum 1 are COMMENT lines, so are BLANK lines
;------------------------------------------------------------------------------
;first we need the addressing stuff.
;You may either specify a full ZONE:NET/NODE.POINT@DOMAIN or just the address
;with the domain name separately after the DOMAIN phrase.
ADDRESS 2:512/10.0 ;If the POINT part is not zero in the FIRST address
;listed, RBBSMail assumes you run as a POINT node.
ADDRESS 2:512/5.0 ;You may specify up to 10 extra (AKA) addresses
ADDRESS 2:2/508.0 ;AKA addresses are ignored for point setup
ADDRESS 8:998/0.0
ADDRESS 8:998/1.0
;------------------------------------------------------------------------------
;Common name of the network of which you are a member with your system's
;PRIMARY nodenumber. (RBBSNet, FIDONET, Eggnet, AlterNet or whatever net).
DOMAIN fidonet
;------------------------------------------------------------------------------
; You may also have POINTS serviced by your system, so you have to tell
; RBBSMAIL what the number of the POINTNET is. There is one restriction,
; the number of your pointnet _MUST_ be the HIGHEST NUMBER in your list
; of nets!!
PRIVATENET 9999 ;Netnumber of private POINT network. This is MANDATORY
;for both point AND boss!!
;------------------------------------------------------------------------------
;Where to find compressed mailbunldes
NETFILE C:\BT2\FILES
;------------------------------------------------------------------------------
;Where to put the outgoing mailbundles
HOLD C:\BT2\HOLD
;------------------------------------------------------------------------------
;This is to identify any ZONE or ECHO gates you send to or receive from,
;followed by the NET/NODE numbers that should ALWAYS appear in the SEEN-BY
;lines in messages adressed to that gate. Normally, the SEEN-BY line to an
;ECHOgate or ZONEgate will only contain the gate's NET/NODE and that of your
;own system (and, perhaps your own gateway AKA NET/NODE, if you have one).
;In case you are not the only system in your net calling the gate, the NET/NODE
;numbers of those other systems should also appear in the SEEN-BY line, UNLESS
;the gate also is your echo host (confused?)
;In all cases, the NET/NODE number should be in numeric order. Having a short
;SEEN-BY line keeps down the costs for ZONEand ECHO gates.
;It is assumed that mail, once send TO the gate will never get
;BACK from the gate to your system. You can have up to 25 gates defined. In
;the example, all messages to 2:2/1 will have "SEEN-BY: 1/2 512/10 101" as
;SEEN-BY line
;GATE is ignored for POINT setups.
;
GATE 1:1/2 1/2 512/10 999/999
GATE 2:2/1 2/1 512/10 999/999
GATE 2:28/0 28/0 512/1 10 999/99
GATE 3:3/2 3/2 512/10 999/999
;------------------------------------------------------------------------------
;Fake zone number of the DOMAIN you are the inbound Network Gateway for,
;followed by the origin line that replaces the origin line of incoming
;echomail from that network
INDOMAIN 8 RBBSNetwork Gateway to Europe (2:2/508.0)
;------------------------------------------------------------------------------
;RBBS-PC uses a SYSOP alias
SYSALIAS Buck Rogers
;------------------------------------------------------------------------------
;The SYSOP's real name
SYSOP John Sysop
;------------------------------------------------------------------------------
SIZE 9000 ;maximum size for TOSSing messages
;------------------------------------------------------------------------------
SECURITY 4 ;default security for TOSSed messages
;------------------------------------------------------------------------------
; This tells RBBSMail what packer it should invoke. If you use the -OB or -OF
; commandline switches, an external packer like oMMM or mOOO should be
; configured here
; If you use RBBSMail's internal mailpacker by using either the -FA or -OF
; command switch, you need not configure the PACKER phrase. You then MAY
; configure the ARCmail options below
PACK RUN_OMMM.BAT
;alternative methods:
;pack oMMM -sa -j
;pack ARCMAIL.EXE
;------------------------------------------------------------------------------
;RBBSMail can run the internal or external mailpacker (see above) after a
;certain number of messages have been exported. This keeps the individual
;mailbundles relatively small in size, which improves the performance if the
;destination node runs ConfMail or QM.
MAXOUT 100 ;# msg generated after which to shell to the packer
;------------------------------------------------------------------------------
;type of compression to use for individual destinations. A total of 100 nodes
;can be listed. Full ZONE:NET/NODE addresses must be listed.
;The old trusted ARCA is the default. If a node is not listed here, he gets
;ARCmail, compressed by ARCA.COM
;This is only applicable if you use RBBSMail's internal ARCmailer by giving
;either the -FA or the -OF option.
;
PAKto 2:512/10 ; this node gets PAK format mailbundles
ARJto 2:555/666 ; this one gets ARJ packed mailbundles
LHAto 2:1010/2 ; he prefers LHA compressed mailbundles
ZIPto 8:900/2 ; but these guys can only handle ZIPped mailbundles
ZOOto 8:999/7 ; and finally a ZOO lover
;------------------------------------------------------------------------------
;this line causes all redundant Ctrl-A kludges to be removed from all
;incoming echomail.
NoStinkingKludgeLines
;------------------------------------------------------------------------------
;set this option if you never want invalid echomail returned to the sender
NoRts
;------------------------------------------------------------------------------
;set this option if you want Secure Mail always enabled
SecureMail
;------------------------------------------------------------------------------
;name of the logfile to use. If not specified, RBBSMAIL.LOG will be used.
StatusLog
;------------------------------------------------------------------------------
;level of detail for logfile, from 0 to 4.
LogLevel 4
;------------------------------------------------------------------------------
;Amount of msg IDs to retain when checking for messages. Can be 0....3200,
;default is 512. Value of 0 disables duplicate checking, which runs a bit
;faster
DupSize 1024
;------------------------------------------------------------------------------
;If you want to conserve some space in your RBBS-PC conference files, set the
;StripSeen option. RBBSMail will then remove all SEEN-BY and PATH lines from
;messages imported to RBBS-PC style message bases.
StripSeen
;------------------------------------------------------------------------------
;This phrase tells RBBSMail to stamp local messages with the CURRENT date, not
;with the date the message was originally entered. If you kill messages by
;age, then the message age will be calculated from the moment the message
;arrived on your system
ImportDate
;------------------------------------------------------------------------------
;This phrase tells RBBSMail to store all local messages written to a FIDO style
;(*.MSG) message base in Opus/MAximus format. Extra date/time info is stored
;in the message header, which allows you to maintenance on the message bases
;using Opus or Maximus utilities like Renum or ReplyLink.
OpusDate
;------------------------------------------------------------------------------
;Kill messages without human readable contents
KillNull
;------------------------------------------------------------------------------
;Normally, Comments and Private messages to Sysop aren't exported. In case
;you have a co-sysop running as one of your points, he may wish to see
;comments and private messages to sysop as well. You can tell RBBSMail to
;export comments and private messages to sysop with this configuration phrase.
;However, be warned that potentially ANYONE can read whatever confidential
;messages or comments are adressed to sysop once the messages have left your
;system!!
ExportComments
; That's all!